From 57f9831dd431e52c2e90e02f7a65385bdabfcf24 Mon Sep 17 00:00:00 2001 From: =?utf8?q?=3D=3FUTF-8=3Fq=3FFabi=3DC3=3DA1n=3D20Ezequiel=3D20Gallina?= =?utf8?q?=3F=3D?= Date: Thu, 17 May 2012 00:03:34 -0300 Subject: [PATCH] `python-check' now can have named buffers on its own depending the command launched. New vars: + python-check-buffer-name --- lisp/progmodes/python.el | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/lisp/progmodes/python.el b/lisp/progmodes/python.el index 5406d74f69e..2f886a5b803 100644 --- a/lisp/progmodes/python.el +++ b/lisp/progmodes/python.el @@ -2149,6 +2149,12 @@ The skeleton will be bound to python-skeleton-NAME." :type 'string :group 'python) +(defcustom python-check-buffer-name + "*Python check: %s*" + "Buffer name used for check commands." + :type 'string + :group 'python) + (defvar python-check-custom-command nil "Internal use.") @@ -2170,7 +2176,9 @@ Runs COMMAND, a shell command, as if by `compile'. See (save-some-buffers (not compilation-ask-about-save) nil) (let ((process-environment (python-shell-calculate-process-environment)) (exec-path (python-shell-calculate-exec-path))) - (compilation-start command))) + (compilation-start command nil + (lambda (mode-name) + (format python-check-buffer-name command))))) ;;; Eldoc -- 2.30.2